Electronic signature for Change Proposal

Hello,

We are trying to test if electronic signature can be implemented for change proposal. For example, the CP manager who would be applying the CPs will have to do electronic signatures before the changes are applied.

Is there a sample script or if someone can provide an idea how to go about it?

thanks
SystemAdmin - Fri Feb 15 06:13:59 EST 2013

Re: Electronic signature for Change Proposal
SystemAdmin - Fri Feb 15 07:17:30 EST 2013

Hi

Electronic signatures in Doors are applied to baselines and there is a button to place a signature. It makes no sense to write script which generate such signatures. It is more attractive to write a script which signs a check from Warren Buffet.

Best regards
Wolfgang

Re: Electronic signature for Change Proposal
SystemAdmin - Fri Feb 15 07:41:27 EST 2013

SystemAdmin - Fri Feb 15 07:17:30 EST 2013
Hi

Electronic signatures in Doors are applied to baselines and there is a button to place a signature. It makes no sense to write script which generate such signatures. It is more attractive to write a script which signs a check from Warren Buffet.

Best regards
Wolfgang

Thank you for your reply.

However, I do not want the electronic signatures for baselines. But want to implement it for CPS. Is there a way to do so?

Re: Electronic signature for Change Proposal
SystemAdmin - Fri Feb 15 07:58:18 EST 2013

SystemAdmin - Fri Feb 15 07:41:27 EST 2013
Thank you for your reply.

However, I do not want the electronic signatures for baselines. But want to implement it for CPS. Is there a way to do so?

All I know is: You can create a baseline and sign it. If only one CP is placed in a module this may help. If your modul contains 100 CPs or more, each of them shall be signed by different persons, it is better to use an other tool.

You can sign a module. Thats it!

Re: Electronic signature for Change Proposal
llandale - Fri Feb 15 11:27:59 EST 2013

DOORS "Signatures" only apply to Baselines, so you will need to code this yourself.

I would say the process you have for "approving" a CP would include concent from the module owner; and not try to implement this in DOORS.

Prefered: You can figure out who applied the CP by looking at the CP object's History, who change "CP Attr-Status" to "Applied". Thus, someone applying the CP is effectively taking responsibility for it. It would be relatively easy to have an Attr-DXL that looks through History and displays the name of the applier, if any.

Discouraged: You could have a post-attribute-save trigger such that if the Attribute is "CP Attr-Status" and the value is "Applied", it sets a string attribute in the module "AppliedSignature" with the name of the current user and the date.

If you want one person to "sign" (approve) it (the owner of the spec) and another to "apply" it (some DOORS admin), then you will have a harder time preventing an "apply" to a CP that is not yet "signed". My first thought would be to find a way to prevent the CP from being "Approved" unless it is somehow "signed". Perhaps a pre-attr-save trigger, if the nominated value is "Approved", then do some checking, possibly dis-allowing the change.

-Louie